Skip to content

fix: sync pyproject.toml version with release-please and use inline marker#14

Merged
justinmerrell merged 1 commit intomainfrom
fix/release-please-version-sync
Mar 30, 2026
Merged

fix: sync pyproject.toml version with release-please and use inline marker#14
justinmerrell merged 1 commit intomainfrom
fix/release-please-version-sync

Conversation

@justinmerrell
Copy link
Copy Markdown
Contributor

Summary

  • Fixes publish pipeline failure (400 Bad Request) caused by pyproject.toml being stuck at 0.2.0 while release-please manifest had 0.3.1
  • Replaces broken extra-files TOML/jsonpath config with the x-release-please-version inline comment marker approach
  • Updates pyproject.toml version to 0.3.1 to match the current release

Test plan

  • task check passes (lint, types, format, 219 tests)
  • Merge and verify the next release-please PR includes pyproject.toml in its changeset
  • Verify publish jobs succeed on the next release

Fixes: https://github.com/musher-dev/python-sdk/actions/runs/23755519953

🤖 Generated with Claude Code

…arker

Release-please was not updating pyproject.toml because the extra-files
TOML/jsonpath config was silently ignored. This left the version stuck
at 0.2.0 while the manifest had 0.3.1, causing publish jobs to fail
with 400 Bad Request (duplicate version on PyPI).

- Update pyproject.toml version to 0.3.1 with x-release-please-version
  inline comment marker for reliable future updates
- Simplify extra-files config to use the Generic updater with the marker

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@justinmerrell justinmerrell merged commit e821dc3 into main Mar 30, 2026
6 checks passed
@justinmerrell justinmerrell deleted the fix/release-please-version-sync branch March 30, 2026 17:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant